LinuxQuestions.org - [SOLVED] This is it! Blowing out windows but first, a LILO question et al...

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - This is it! Blowing out windows but first, a LILO question et al... (https://www.linuxquestions.org/questions/slackware-14/this-is-it-blowing-out-windows-but-first-a-lilo-question-et-al-865971/)

Quote:

Originally Posted by Darth Vader (Post 4276701)

Sadly, looks like the right idea ... Do it again.

Here it is:

Code:

root@darkstar:/# mkfs.ext4 /dev/sda1

mke2fs 1.41.11 (14-Mar-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

640848 inodes, 2560248 blocks

128012 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=2625634304

79 block groups

32768 blocks per group, 32768 fragments per group

8112 inodes per group

Superblock backups stored on blocks: 

        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632



Writing inode tables: done                            

Creating journal (32768 blocks): done

Writing superblocks and filesystem accounting information: done



This filesystem will be automatically checked every 21 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

root@darkstar:/# mkfs.ext4 /dev/sda2

mke2fs 1.41.11 (14-Mar-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

640848 inodes, 2560000 blocks

128000 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=2621440000

79 block groups

32768 blocks per group, 32768 fragments per group

8112 inodes per group

Superblock backups stored on blocks: 

        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632



Writing inode tables: done                            

Creating journal (32768 blocks): done

Writing superblocks and filesystem accounting information: done



This filesystem will be automatically checked every 29 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

root@darkstar:/#

Let's see what say 'mount -a' and 'df -h'. If everything is perfect, we can start the real migration. :)

Hi Darth:

I am really sorry that this taking up so much of your time.

I would understand if you would like to stop this and 'go back to work' or 'go back to your family' or what ever...

Quote:

Originally Posted by Darth Vader (Post 4276710)

Let's see what say 'mount -a' and 'df -h'. If everything is perfect, we can start the real migration. :)

Here it is:

Code:

root@darkstar:/# mount -a

mount: wrong fs type, bad option, bad superblock on /dev/sda1,

      missing codepage or helper program, or other error                                                              

      In some cases useful info is found in syslog - try                                                              

      dmesg | tail  or so                                                                                            



mount: wrong fs type, bad option, bad superblock on /dev/sda2,

      missing codepage or helper program, or other error

      In some cases useful info is found in syslog - try

      dmesg | tail  or so



mount: devpts already mounted or /dev/pts busy

root@darkstar:/# df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/root              39G  8.1G  29G  23% /

/dev/sda8              81G  9.6G  68G  13% /home

tmpfs                1.5G  296K  1.5G  1% /dev/shm

root@darkstar:/# mount -a

mount: wrong fs type, bad option, bad superblock on /dev/sda1,

      missing codepage or helper program, or other error

      In some cases useful info is found in syslog - try

      dmesg | tail  or so



mount: wrong fs type, bad option, bad superblock on /dev/sda2,

      missing codepage or helper program, or other error

      In some cases useful info is found in syslog - try

      dmesg | tail  or so



mount: devpts already mounted or /dev/pts busy

root@darkstar:/#

Code:

oot@darkstar:/# df -h

Filesystem            Size  Used Avail Use% Mounted on

/dev/root              39G  8.1G  29G  23% /

/dev/sda8              81G  9.6G  68G  13% /home

tmpfs                1.5G  296K  1.5G  1% /dev/shm

root@darkstar:/#

Quote:

Originally Posted by Robert.Thompson (Post 4276711)

Hi Darth:

I am really sorry that this taking up so much of your time.

I would understand if you would like to stop this and 'go back to work' or 'go back to your family' or what ever...

Don't worry, I'm at job. And my job is the administration of a bunch of servers. While I talk with you, my right eye is on servers data. ;)

BAD NEWS, you should boot on your new system on next 2 hours, or we should continue tomorrow.

Quote:

Originally Posted by Darth Vader (Post 4276716)

Do you want me to reboot now?

Do you want to continue tomorrow?

I can do whatever you want...

Then, I want the dump of command:

Code:

sfdisk -l /dev/sda

Quote:

Originally Posted by Darth Vader (Post 4276720)

Then, I want the dump of command:

Code:

sfdisk -l /dev/sda

Here it is:

Code:

root@darkstar:/# sfdisk -l /dev/sda



Disk /dev/sda: 19457 cylinders, 255 heads, 63 sectors/track

Warning: extended partition does not start at a cylinder boundary.

DOS and Linux will interpret the contents differently.

Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0



  Device Boot Start    End  #cyls    #blocks  Id  System

/dev/sda1  *      0+  1274-  1275-  10240992+  83  Linux

/dev/sda2      1274+  2549-  1275-  10240000  83  Linux

/dev/sda3      2549+  3123-    574-  4608000  82  Linux swap

/dev/sda4      3123+  19457-  16334- 131200001    5  Extended

/dev/sda5      3123+  3378-    255-  2048000  83  Linux

/dev/sda6      3378+  3633-    255-  2048000  83  Linux

/dev/sda7      3633+  8733-  5100-  40960000  83  Linux

/dev/sda8      8733+  19457-  10724-  86139904  83  Linux

root@darkstar:/#

Where are you and what time is it there?

I'm from/in Romania/Europe, and there is 21:47 ... :D

Then, we have the right definitions on /etc/fstab and these partitions are very ... ext4. Strange! :)

So, what say /var/log/syslog about these partitions? :)

Quote:

Originally Posted by Darth Vader (Post 4276737)

Sorry Darth, but how much of the file do you want to see and which editor should I use?

Quote:

Originally Posted by Robert.Thompson (Post 4276771)

Sorry Darth, but how much of the file do you want to see and which editor should I use?

Well, try something like 'mount /dev/sda1' and paste here the last 20-30 lines from syslog.

AS editor, for pasting, you can use kwrite, for example.

kwrite /var/log/syslog

You should to remember to no change the file.

Quote:

Originally Posted by Darth Vader (Post 4276777)

Here it is:

Code:

Mar  2 14:15:58 darkstar kernel: CE: hpet increasing min_delta_ns to 15000 nsec

Mar  2 14:29:17 darkstar kernel: EXT4-fs (sda1): Unrecognized mount option "umask=077" or missing value

Mar  2 14:29:17 darkstar kernel: EXT4-fs (sda2): Unrecognized mount option "umask=000" or missing value

Mar  2 14:34:29 darkstar kernel: EXT4-fs (sda1): Unrecognized mount option "umask=077" or missing value

Mar  2 14:34:29 darkstar kernel: EXT4-fs (sda2): Unrecognized mount option "umask=000" or missing value

Mar  2 14:37:46 darkstar kernel: sr1: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar kernel: Buffer I/O error on device sr1, logical block 0

Mar  2 14:38:12 darkstar kernel: end_request: I/O error, dev sr1, sector 0

Mar  2 14:38:12 darkstar last message repeated 39 times

Mar  2 15:14:35 darkstar kernel: EXT4-fs (sda1): Unrecognized mount option "umask=077" or missing value

Here we go! You modified the /etc/fstab like I said?

Code:

/dev/sda3        swap            swap        defaults        0  0

/dev/sda7        /                ext4        defaults        1  1

/dev/sda8        /home            ext4        defaults        1  2

/dev/sda1        /winxp          ext4        defaults        1  2

/dev/sda2        /windata        ext4        defaults        1  2

#/dev/cdrom      /mnt/cdrom      auto        noauto,owner,ro  0  0

/dev/fd0        /mnt/floppy      auto        noauto,owner    0  0

devpts          /dev/pts        devpts      gid=5,mode=620  0  0

proc            /proc            proc        defaults        0  0

tmpfs            /dev/shm        tmpfs      defaults        0  0

Quote:

Originally Posted by Darth Vader (Post 4276787)

Here we go! You modified the /etc/fstab like I said?

Code:

/dev/sda3        swap            swap        defaults        0  0

/dev/sda7        /                ext4        defaults        1  1

/dev/sda8        /home            ext4        defaults        1  2

/dev/sda1        /winxp          ext4        defaults        1  2

/dev/sda2        /windata        ext4        defaults        1  2

#/dev/cdrom      /mnt/cdrom      auto        noauto,owner,ro  0  0

/dev/fd0        /mnt/floppy      auto        noauto,owner    0  0

devpts          /dev/pts        devpts      gid=5,mode=620  0  0

proc            /proc            proc        defaults        0  0

tmpfs            /dev/shm        tmpfs      defaults        0  0

I did modify it, did I not?

The 'label' remained but it is type ext4.

Is there something wrong?

I think that I am confused, again. Sorry.

Quote:

Originally Posted by Robert.Thompson (Post 4276798)

I did modify it, did I not?

The 'label' remained but it is type ext4.

Is there something wrong?

I think that I am confused, again. Sorry.

You should modify also the mount options, we don't care about mountpoint.

Code:

/dev/sda1        /winxp          ext4        defaults        1  2

/dev/sda2        /windata        ext4        defaults        1  2

Because, if NOT, here we go:

Code:

Mar 2 15:14:35 darkstar kernel: EXT4-fs (sda1): Unrecognized mount option "umask=077" or missing value