errors=remount -ro   should be:  errors=remount,ro

user, noauto   should be  user,noauto

Maybe those changes will fix it.

erdos wrote:

system is in read-only mode after attempted ascii upgrade.

As in your disks are mounted read only? That seems to be more of a disk problem. What does your partition layout and filesystems look like?

output of 'fdisk -l', partition sda5~7 are Linux partitions, I've a multi-boot system.

root@(none):~# fdisk -l 
Device   BOOT   START   End Sectors Size ID  Type
/dev/sda1   *              63      62929439   62929377   30G  7   HPFS/NTFS/exFAT
/dev/sda2         106027047    143775701    37748655   18G  a5   FreeBSD
/dev/sda3         143806320    156295439    12489120     6G   c   W95 FAT32 (LBA)
/dev/sda4          62930942      106027007   430960666   20.6G   f   W95  Ext'd (LBA)
/dev/sda5           62930944      82460671    19529728      9.3G    83 Linux
/dev/sda6            82462720      85053439    2590720       1.2G    82 Linux swap / Solaris
/dev/sda7            85055488      106027007    20971520    10G     83   Linux

output of /etc/fstab:

UUID= ' -------'  /   ext4   errors=remount -ro 0  1
UUID= ' -------'  /home  ext4  defaults  0  2
UUID= ' -------'  none  swap   sw 0 0
/dev/sr0    /media/cdrom0  udf,iso9660  user, noauto  0  0

erdos wrote:

msi wrote:

Ok, I see. First, I'd try setting sources.list back to Jessie and then run apt-get update and apt-get upgrade. If that goes well, I'd reboot and see how that goes.

Btw, it's a good idea to use code tags when posting config files. That makes it more readable.

The issue remains unresolved because the wifi is not working and system is in read-only mode after attempted ascii upgrade.

The best thing you can do is backup any data/documents then do a fresh installation of whatever distro you want to install. It'll be far quicker than trying to recover a a borked install.

Quite likely. At least if don't know how to debug it yourself and can somewhat approximate the work needed. Still trying to fix it has more of a learning effect than just reinstalling. Up to @erdos preference i guess.

msi wrote:

Ok, I see. First, I'd try setting sources.list back to Jessie and then run apt-get update and apt-get upgrade. If that goes well, I'd reboot and see how that goes.

Btw, it's a good idea to use code tags when posting config files. That makes it more readable.

The issue remains unresolved because the wifi is not working and system is in read-only mode after attempted ascii upgrade.

The best thing you can do is backup any data/documents then do a fresh installation of whatever distro you want to install. It'll be far quicker than trying to recover a a borked install.

system is in read-only mode after attempted ascii upgrade.

As in your disks are mounted read only? That seems to be more of a disk problem. What does your partition layout and filesystems look like?

Ok, I see. First, I'd try setting sources.list back to Jessie and then run apt-get update and apt-get upgrade. If that goes well, I'd reboot and see how that goes.

Btw, it's a good idea to use code tags when posting config files. That makes it more readable.

The issue remains unresolved because the wifi is not working and system is in read-only mode after attempted ascii upgrade.

msi wrote:

Btw, it's a good idea to use code tags when posting config files. That makes it more readable.

Done (for the second time).

Looks like something to mention in a forum code of conduct to be.

Btw, it's a good idea to use code tags when posting config files. That makes it more readable.

Done (for the second time).

Btw, it's a good idea to use code tags when posting config files. That makes it more readable.

With that kind of error messages occuring, apt-get should refuse to perform any dist-upgrade, which it seemingly did in your case. So, unless you did not "try using -f" or anything else in that direction and also changed back your sources.list to Jessie and ran apt-get update after that, your system should  actually be fine. So, did you try any other commands to make the upgrade happen or forget to revert your apt sources to Jessie?

What does /etc/apt/sources.list look like on that system?

I can only boot into command line, and wifi isn't working.  the system is in read only mode and home directory isn't mounted. 
i have run '-f' but it returns error since system is locked in read-only mode.

i've run into this error when i tried to upgrade from devuan jessice to ascii a couple months ago (March 24th):

root@debian:/home/erdos# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. 
The following packages have unmet dependencies: 
initscripts : Depends: sysv-rc or file-rc but it is not installable libncurses5 
: Depends: libtinfo5 (= 5.9+20140913-1+b1) but 6.0+20161126-1+deb9u1 is installed sysvinit-core 
: Depends: sysv-rc or file-rc but it is not installable sysvinit-utils 
: Depends: init-system-helpers (>= 1.25~) but 1.24+devuan1.0 is installed E: Unmet dependencies. Try using -f.

after reboot the system, i can only log into command line, but my home directory is not mounted, wifi is not working.

With that kind of error messages occuring, apt-get should refuse to perform any dist-upgrade, which it seemingly did in your case. So, unless you did not "try using -f" or anything else in that direction and also changed back your sources.list to Jessie and ran apt-get update after that, your system should actually be fine. So, did you try any other commands to make the upgrade happen or forget to revert your apt sources to Jessie?

What does /etc/apt/sources.list look like on that system?

i've run into this error when i tried to upgrade from devuan jessice to ascii a couple months ago (March 24th):

root@debian:/home/erdos# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. 
The following packages have unmet dependencies: 
initscripts : Depends: sysv-rc or file-rc but it is not installable libncurses5 
: Depends: libtinfo5 (= 5.9+20140913-1+b1) but 6.0+20161126-1+deb9u1 is installed sysvinit-core 
: Depends: sysv-rc or file-rc but it is not installable sysvinit-utils 
: Depends: init-system-helpers (>= 1.25~) but 1.24+devuan1.0 is installed E: Unmet dependencies. Try using -f.

after reboot the system, i can only log into command line, but my home directory is not mounted, wifi is not working.

my laptop is thinkpad t60 with wifi built in.

this seems to be some init messed up when ascii is still in testing, now that ASCII has been released.  is there a way to recover the system without reinstallation?